home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 22
/
Cream of the Crop 22.iso
/
os2
/
jumpkey.zip
/
README.CID
< prev
next >
Wrap
Text File
|
1996-06-15
|
12KB
|
401 lines
(c) Copyright International Business Machines Corporation 1996.
VERSION 2.3.0 15 June 1996
How to Install JumpKey/2 from a LAN Server
==========================================
If you want to install JumpKey/2 on several
workstations, you can install it without using diskettes.
Follow these steps:
o Create a directory on the LAN server to store the JumpKey/2
files, for example:
MKDIR J:\JUMPKEY
o Copy each JumpKey/2 diskette into this directory using
the XCOPY command, for example:
XCOPY a:*.* J:\JUMPKEY /S
o Install JumpKey/2 by typing INSTALL at the command prompt
and pressing Enter.
How to Install JumpKey/2 from a Diskette or CD-ROM
==================================================
To install JumpKey/2 onto your workstation from diskette or CD-ROM,
for example, type INSTALL, and press Enter.
How to Create a Response File
=============================
Response files are used to provide data that is normally entered manually
when JumpKey/2 is installed. A sample response file is provided
as a template for your use. This file,
JMP230.RSP
along with the .CMD file that starts the install:
JUMPCID.CMD
allow for an automated hands-off installation. To customize the
installation for your environment, you must modify the response
file or the .CMD file.
Response File Format and Keywords
=================================
This product supports the following keywords:
---------------------------------------------
CFGUPDATE (required)
Specifies whether the CONFIG.SYS file is automatically updated.
Valid values for this keyword are:
AUTO Automatically updates CONFIG.SYS
MANUAL Does not update CONFIG.SYS
JumpKey does not require that CONFIG.SYS be updated unless you want to
run it from the command line.
---------------
COMP
Specifies the unique name of a component of the product
for which passed information applies.
There can be a maximum of 100 components.
The COMP value must match the NAME keyword of the COMPONENT entry in the
package file.
JumpKey 2.2.1 provides 3 components:
JMPBASE - base code. Required for all installations
JMPUSE - US 101-Key Keyboard Support
JMPUKE - UK 102-Key Keyboard Support
Always specify
COMP=JMPBASE
then choose ONE keyboard support package. Do NOT choose both:
COMP=JMPUSE
or
COMP=JMPUKE
---------------
DELETEBACKUP
Specifies whether to delete only the backup versions of the
product or to delete the entire product.
Valid values for this keyword are YES and NO.
It is required because an existing
dialog requests this information in the attended mode.
If an unattended delete is attempted
and the DELETEBACKUP is not present in the response file, the
deletion fails with an EPFIE212 error.
---------------
FILE
Provides the new default path for the file directory.
This keyword is used only for installation processing.
This FILE value is used in place of the FILE keyword of the PATH entry in
the package file.
---------------
OVERWRITE
Specifies whether to automatically overwrite files during
installation. Valid values for this keyword are YES and NO.
---------------
SAVEBACKUP
Specifies whether to save a backup version of the product when it
is updated. Valid values for this keyword are YES and NO.
It is required for unattended processing because an existing
dialog requests this information in the attended mode.
---------------
Response File Details
=====================
A response file is a flat ASCII file
that consists of a series of lines separated by newline sequences
(0x0A, 0x0D, or a combination of these two sequences).
Each line in a response file has a maximum line length of 255 bytes.
A response file has two kinds of lines:
Comment lines
-------------
Comment lines contain only white space characters
or have either an asterisk (*) or a semicolon (;)
as the first nonwhite space character on the line.
Response lines
--------------
Response lines are used by Software Installer
to determine the options
and configurations to install on the target system.
Response lines have the following syntax:
keyword = value
Keywords cannot contain imbedded spaces.
Keywords are not case-sensitive.
You can group keywords together
in value lists using the following syntax:
keyword = (
keyword1 = value
keyword2 = value
.
.
keywordn = value
)
Using Command Line Parameters
=============================
If no parameters are specified when the executable file is started,
the installation is attended.
To install in an unattended mode, the /X parameter must be used.
Unattended includes what is sometimes referred to as lightly attended.
In the lightly attended mode, someone might have to start
an executable file or insert diskettes.
If the value of any of the parameters contains spaces,
use double quotes to enclose the value.
Values can be upper or lower case.
Parameters can be in any order.
<command> /A:<action>
/C:JMP230.ICF
/L:<xpos,ypos>
/L1:<error log>
/L2:<history log>
/O:<originating system>
/P:"IBM JumpKey/2"
/R:JMP230.RSP
/S:<source location>
/T:<install target directory>
/TU:<update CONFIG.SYS directory>
/X <interactive_flag>
The /A, /C, and /P parameters are required for an installation
that is started with the EPFINSTS command.
If the action is an install or an update, the /O is also required.
Note:
The drive/directory/filename path is required
for all log parameters specified
with the INSTALL.EXE or EPFIDLDS.EXE commands.
The directories for log files must exist before starting the commands.
Parameter Definitions
=====================
The command prompt parameters are:
/A:<action>
Specifies the action of the EPFINSTS.EXE.
If you use this parameter,
the main window of the installation is not displayed.
If you do not use this parameter,
the installation starts normally with all windows displayed.
Valid values for this parameter are:
'D' For delete
'I' For install
'R' For restore
'U' For update
The installation program sets the EPFIACTION installation
variable to the action.
/C:JMP230.ICF
Specifies the name and location of the catalog file that
you want to be opened automatically.
If the catalog file is located on a host session, the
host session ID must precede the catalog file name. If the
catalog file is located on a drive, a drive and directory must
precede the catalog file name.
The installation program sets the EPFICATALOG installation
variable to the name of the catalog file.
The following examples show how to use
this parameter for each installation source.
o For Drive: /C:A:\DISK1.ICF
o For MVS: /C:B:EPF.V1R2M0.SEPFBENU(EPFICAT)
o For VM: /C:"B:EPFICAT ENUEPF12 *"
o For VSE: /C:B:LIB.SUBLIB.MEMBERNAME.MEMBERTYPE
If only the host session ID is specified,
for example, B:,
the Open catalog window
is displayed with B: as the default session or drive.
/L:<xpos,ypos>
Specifies the initial horizontal and vertical coordinates
of the initial installation window on the Workplace Shell
relative to the lower-left corner of the screen.
If this parameter is specified,
all previously saved default positions are overridden.
The installation program sets the EPFIWNDCOORDS installation
variable to the coordinates of the Installation and Maintenance window.
/L1:<error log>
Specifies the drive, path, and file name of the error log file.
The installation program sets the EPFIERRORLOG installation
variable to the name of the error log.
The drive/directory/filename path is required.
The directory for the log file must already exist.
All lines logged to the error file are prefixed with a time stamp.
The time stamp has the following format:
YYYY-MM-DD HH:mm:SS:cc
Where:
YYYY is the year.
MM is the month.
DD is the day.
HH is the hour.
mm is the minute.
SS is the second.
cc is the hundredth of a second.
The date and time separators are the current user-defined settings in
the Country object of the System Settings folder.
The default separators are the hyphen and the colon, respectively.
Example of using the /L1 parameter to create ERROR.LOG file in the
C:\ABC\ directory:
/L1:C:\ABC\ERROR.LOG
/L2:<history log>
Specifies the drive, path, and file name of the history log file.
The installation program sets the EPFIHISTORYLOG installation
variable to the name of the history log.
The drive/directory/filename path is required.
The directory for the log file must already exist.
If this parameter is not specified, no history log is maintained.
All lines logged to the history file are prefixed with a time stamp.
The time stamp has the following format:
YYYY-MM-DD HH:mm:SS:cc
Where:
YYYY is the year.
MM is the month.
DD is the day.
HH is the hour.
mm is the minute.
SS is the second.
cc is the hundredth of a second.
The date and time separators are the current user-defined settings in
the Country object of the System Settings folder.
The default separators are the hyphen and the colon, respectively.
Example of using the /L2 parameter to create HISTORY.LOG file in the
C:\ABC\ directory:
/L2:C:\ABC\HISTORY.LOG
/O:<originating system>
Specifies the originating system of the installation.
Valid values are:
o DRIVE
o MVS
o VM
o VSE
The installation program sets the EPFISOURCE installation
variable to one of these values.
/P:"IBM JumpKey/2"
Provides the name of the product for the specified action.
If you do not use this parameter, the installation
comes up normally with all windows displayed.
/R:JMP230.RSP
Specifies the drive, path, and file name
of the specific response file.
/S:<source_location>
Specifies the drive and path
that contains the source files to install.
If this parameter is not specified,
the value of the HOSTLOC keyword is not overridden.
Example:
/S:L:\XYZ
/T:<install target directory>
Specifies the drive and path
where the product files are installed.
If this parameter is specified, it overrides the FILE paths
that are specified in the response files and the package files.
Example:
/T:C:\JUMPKEY
/TU:<update target CONFIG.SYS directory>
Specifies the drive and path of the target CONFIG.SYS to be updated.
If this parameter is not specified,
the CONFIG.SYS files are updated as specified
in the product's package file.
Example:
/TU:C:\
/X
Specifies that the action is unattended.
If you do not specify all of the information needed for the action
to complete, an error occurs.
When you specify the /X option, no progress indication is shown
and all error messages are logged to the error file you specified using
the /L1 parameter.
If you do not specify this option, the user is prompted
for any information that the EPFINSTS.EXE needs to complete the
action. In this attended mode of
action, progress indication is shown and error messages are
displayed to the user in secondary windows.
The installation program sets the EPFINONINTERACT installation
variable to YES if the /X parameter is specified.
Return Codes from JumpKey/2 to a Controller
===========================================
JumpKey/2 returns the following return codes to a
software distribution manager (SDM):
o Successful installation.
00 00 No messages were logged.
o Successful installation.
The workstation operating system will be restarted.
Do not call Software Installer again.
FE 00 No messages.
FE 04 Warning messages were logged.
FE 08 Error messages were logged.
FE 12 Severe error messages were logged.
o Successful installation.
Restarting the workstation operating system occurs.
Start the installation again.
o Unexpected condition encountered during installation.
16 00 Incorrect invocation of installation program
16 04 Messages were logged.
All return codes are two-byte hexadecimal values.